File Location for Automatic Update
The files for updating the device can be stored on any standard Web (HTTP/S), TFTP, or FTP server. The files can be loaded periodically to the device using HTTP/S, TFTP, or FTP. This mechanism can be used even when the device is installed behind NAT and firewalls. The Automatic Update feature is done per file and configured by specifying the file name and URL address of the provisioning server where the file is located. If the device needs to authenticate itself with the server, you can use the same parameters to configure the authentication username and password (for more information, see Access Authentication with HTTP Server). For a description of the parameters for configuring the URLs of the servers of the files, see Automatic Update Parameters.
Below are examples for configuring the file names and their URLs for Automatic Update:
IniFileURL = 'http://www.corp.com/configuration.ini'
CptFileURL = 'http://www.corp.com/call_progress.dat'
AutoCmpFileUrl = 'http://www.corp.com/SIP_F7.20A.008.cmp
FeatureKeyURL = 'https://www.company.com/License_Key.txt'
# configure system
(config-system)# automatic update
(auto-update)# cli-script https://company.com/cli/<MAC>
(auto-update)# startup-script https://company.com/startup/<MAC>
(auto-update)# ini-file http://www.company.com/configuration.ini
(auto-update)# call-progress-tones http://www.company.com/call_progress.dat
(auto-update)# feature-key http://www.company.com/License_Key.txt
(auto-update)# auto-firmware http://www.company.com/SIP_F7.20A.008.cmp
|
●
|
When using the Auto-Update mechanism to upload the Configuration Package file (automatic update > configuration-pkg), if the file is password-protected (encrypted), specify the password using the command automatic update > default-configuration-package-password. |
|
●
|
When using the [IniFileURL] parameter, parameters not included in the file are restored to default settings. If you want to keep the settings of these parameters, use the [IncrementalIniFileURL] parameter instead. |